Skip to content

[bugfix] fix dense model get layer spec#80

Merged
hjh0119 merged 15 commits intomodelscope:mainfrom
hjh0119:fix-dense
Feb 27, 2026
Merged

[bugfix] fix dense model get layer spec#80
hjh0119 merged 15 commits intomodelscope:mainfrom
hjh0119:fix-dense

Conversation

@hjh0119
Copy link
Copy Markdown
Collaborator

@hjh0119 hjh0119 commented Feb 27, 2026

No description provided.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a bug in the layer specification logic for dense models within the Megatron framework. The changes ensure that the num_experts parameter is correctly interpreted, preventing unintended activation of Mixture-of-Experts (MoE) grouped GEMM operations when experts are not configured or explicitly set to zero. This fix improves the robustness and accuracy of model configuration, particularly for non-MoE architectures.

Highlights

  • Bug Fix: Dense Model Layer Specification: Corrected the logic for determining the num_experts and moe_grouped_gemm parameters within the get_layer_spec function. Previously, num_experts defaulted to 0, which could incorrectly enable MoE grouping for dense models or misinterpret the absence of explicit expert configuration.
  • Improved num_experts Handling: Changed the default value for num_experts from 0 to None when it's not explicitly provided in mg_config_dict. This allows for a clearer distinction between a model explicitly configured with zero experts and a model where expert configuration is absent.
  • Accurate MoE Grouped GEMM Activation: Updated the condition for moe_grouped_gemm to activate only when num_experts is explicitly set (i.e., not None), preventing unintended MoE grouping for dense models that do not utilize experts.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • src/twinkle/model/megatron/model/register.py
    • Modified the retrieval of num_experts to default to None instead of 0.
    • Updated the moe_grouped_gemm condition to check if num_experts is not None.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@hjh0119 hjh0119 merged commit 2fa2608 into modelscope:main Feb 27, 2026
1 of 3 checks passed
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request provides a bugfix for determining the layer specification for dense models. The change correctly adjusts the logic to handle the num_experts parameter. Previously, it would default to 0 for non-expert models, but the new implementation ensures it is None when there are no experts (i.e., when the value is missing, None, or 0). This is likely the correct behavior for the downstream get_gpt_layer_with_transformer_engine_spec function to distinguish dense models from Mixture-of-Experts models. The corresponding change to the moe_grouped_gemm flag is consistent and correct. The fix is concise and addresses the issue effectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants